Skip to main content
Version: 5.3.0.0

Process model

Concept​

A process model describes the sequence of steps necessary to process a certain task. In Orchestra, we use a graphical visualisation of the workflows. It is based on BPMN but simplified in favour for the user experience. BPMN is a graphical notation together with a clear semantics to describe the behaviour of a process.

Creation of a process model​

processModel1 processModel2

  • Manual
    This defines a start event for the process which can be triggered externally, for example via a service call or as a sub process model
  • Timer This defines a start event for the process which triggers the workflow dependent of the scheduling configuration
  • Signal This defines a start event for the process which triggers the workflow by receiving the configured signal
  • Error This defines a start event for the process which triggers the workflow in case of an occured error while starting.
  • Monitor This defines a start event for the process which is triggered by an adapter/monitor

Then the process model is created with a default name and configuration By bringing the process model into the focus of the application by clicking on it within the lefthanded scenario element component it is possible to change the configuration of all available properties.

  1. First you enter an appropriate name for the new process model and optionally a short description. Dialog to name and describe a new process model

  2. After clicking the Finish button the process model is created and the panel to design the model is opened. Actually initially this is an empty sheet where the developer has to place the elements of the process model.

Edit a process model metadata​

A process model is configured by changing its properties and by designing its visual representation.

editProcessModelProperties

Design a workflow in a process model​

You can add new scenario elements to your scenario by creating the new element with the green + button in the bottom left corner: createadapterandAddtoPM1

After the element was created you can either add your scenario element to the process model or add a logical function building block as can be seen in the following graphic:

pm_design_xor_workflow

Process model layout​

When a process model is created, elements are initially arranged in a structured layout. Users can reposition elements freely within the designer to organize the workflow according to their needs.

As elements are moved, the connections between them adjust to reflect the new positions, allowing the diagram to be arranged in a way that improves readability.

PMLayout PMLayout

note

Changing the visual layout of elements or connections does not affect the logical execution of the process.

Context menu in process model​

The context menu within a process model can be accessed by selecting the process model element that you want to edit. After selection the context menu will open to the right side of the window.

designPM2

MCP​

The MCP configuration allows you to make a process model available with the Model Context Protocol for an AI-Agent of your choice.

warning

For configuring this setting you will need elevated access on your user

mcp_tool mcp_tool

With the checkbox "Expose as MCP Tool", process models with a manual start event can be published as tools in an MCP server.

These tools can then be accessed in the MCP client through the following setting:

{
  "servers": {
    "orchestra_scenario": {
      "transport": "http",
      "url": "<http/https>://<host>:<port>/scenarios/ai/mcp"
    }
  }
}